-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add deployment settings pointer for concurrency docs #26602
base: master
Are you sure you want to change the base?
Conversation
Deploy preview for dagster-docs ready! Preview available at https://dagster-docs-27esek7ic-elementl.vercel.app Direct link to changed pages: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for adding! copy suggestion inline
@@ -422,7 +422,7 @@ The concurrency key should match the name that the op/asset is tagged with. For | |||
|
|||
A default concurrency limit can be configured for the instance, for any concurrency keys that do not have an explicit limit set: | |||
|
|||
- **Dagster+**: Use the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] | |||
- **Dagster+**: Use the deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Use the deployment settings" reads a little odd to me. Maybe "Edit the concurrency
key in deployment settings via the`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this reads better to me.
Summary & Motivation
Add a pointer that the UI / CLI settings changes are deployment settings
How I Tested These Changes
inspection